-
Notifications
You must be signed in to change notification settings - Fork 667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for setting target path in map config #4694
Add support for setting target path in map config #4694
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Hi! If there is anything else I can help with or questions I can answer please feel free to let me know! Thanks! |
I added the FolderMapping dataclass and made the corresponding changes. I tried for the last couple of hours to get a local supervisor running against the main branch with no success. Here is the error message in case it is helpful:
Anyway, the reason I say that is because there may be issues that I'm not able to test so if you encounter any issues with my changes please let me know and I will do my best to resolve them. Thanks! |
You need a new version of devcontainer -> https://github.com/home-assistant/devcontainer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once #4760 goes this can be rebased off that and then the dataclass moved to addons/data.py
as per pvizeli's suggestion. Looks like its all ready to go at that point.
Co-authored-by: Mike Degatano <[email protected]>
Oh shoot. @pvizeli we can't put this in How about |
@mdegat01 I moved the FolderMapping dataclass to configuration.py as you suggested. If there are any other changes I should make just let me know! |
@jgoakley it looks like there's conflicts with the base branch. Can you rebase and resolve that? Then this is good to get merged. |
Hi @mdegat01, I think I accidently did a merge commit instead of a rebase when clicked "update branch" in GitHub. Sorry about that, I'm not very familiar with rebasing. I also synced my fork and performed a merge in VS Code but I didn't see any conflicts. Is "main" the correct base branch I should be merging into? |
Has been signed meanwhile
@jgoakley all good on the merge vs. rebase. We prefer rebases since it makes the PR easier to review as the only commits are your changes, not the merges. But we squash and merge in the end so it doesn't matter after its merged. Thanks for the contribution 👍 |
Proposed change
Type of change
This change is to add support for configuring the target path for custom addons. In order to persist data outside of the addon container certain paths need to be bound. Currently there are several options to bind path into an addon (data, config, share, etc) but the paths inside the container are set.
Some applications and existing docker images have default storage paths that are not easily changed (if at all). Being able to configre these paths will allow simple integration with these applications. I have created a feature request in the Home Assistant Community Forum that provides some more detail:
https://community.home-assistant.io/t/ability-to-configure-container-target-path-for-custom-addon-such-as-wordpress/635615
Additional information
Checklist
black --fast supervisor tests
)If API endpoints of add-on configuration are added/changed: